Method and system for providing automatic execution of black box strategies for electronic trading

ABSTRACT

A method and system for providing automatic execution of black box trading strategies for electronic trading. A black box trading entity is created from two or more real or synthetic trading entities including real or synthetic contracts or financial instruments. The black box trading entity is automatically traded via one or more electronic trading exchanges.

CROSS REFERENCES TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 60/678,106, filed May 4, 2005, the contents of which as incorporatedby reference.

FIELD OF THE INVENTION

This invention relates to providing electronic information over acomputer network for electronic trading. More specifically, it relatesto a method and system for providing automatic execution of black boxtrading strategies for electronic trading.

BACKGROUND OF THE INVENTION

The trading of stocks, bonds and other financial instruments overcomputer networks such as the Internet has become a very commonactivity. In many countries of the world, such stocks, bonds and otherfinancial instruments are traded exclusively over computer networks,completely replacing prior trading systems such as “open outcry” tradingin trading pits.

Trading of stocks, bonds, etc. typically requires multiple types ofassociated electronic information. For example, to trade stockselectronically an electronic trader typically would like to know anasking price for a stock, a current bid price for a stock, a bidquantity, an asking quantity, current information about the company thetrader is trading such as profit/loss information, a current corporateforecast, current corporate earnings, etc.

The multiple types of associated electronic information have to besupplied in real-time to allow the electronic trader to make theappropriate decisions. Such electronic information is typicallydisplayed in multiple windows on a display screen.

For an electronic trader to be successful, the trader typically developstrading strategies. For example a trading strategy may include executinga trade based on a desired ratio between two trading instruments. Asanother example, a trading strategy may include executing a trade basedon a basis level for a trading instrument.

There are several problems with using manual trading strategies onelectronic trading systems. One problem is that a trader will typicallycreate his/her own trading strategies using disjunct or proprietarytools. For example, a trade may implement his/her own trading strategyin a spreadsheet and manually enter and update current market values oftrading instruments. The trader then must take additional actions toimplement his/her trading strategy based on data form the spreadsheet.

Another problem is that some electronic trading systems allow traders toenter certain data to provide automatic notification of events that arerelated to a trader's trading strategy (e.g., a certain buy price, asell price, a ratio, etc.). However, then a trader must still takemanual actions to execute an electronic trade such as clicking a mouse,making a keyboard input, etc.).

Another problem is that many traders execute trades across manydifferent markets and several different electronic exchanges. Suchtrading typically leads a trader to manual methods to execute a desiredtrading strategy.

Another problem is that many traders desire to execute trades for“synthetic contracts” or contracts that don't really exist on anytrading exchange. For example, a synthetic contract may includeautomatically selling a call and buying a put. Such a synthetic contractdoes not exist on any trading exchange but is desirable to a selectedgroup of traders.

There have been attempts to solve some of the problems with GUIs usedfor electronic trading. For example, U.S. Pat. No. 6,993,504 entitled“User interface for semi-fungible trading,” that issued to Frisen et al.teaches “A user interface and method are disclosed for providing tradingbetween a plurality of semi-fungible and non-fungible goods. A pluralityof book axes are displayed in a single interface, each book axisrepresenting a market for a particular good. Orders for goods aredisplayed as marks on the axes to display the relative value of theorders. A value axis is provided that relates the value of the goodsfrom each market to each other. Thus, a single interface provides themeans to relate the values of different semi-fungible goods. The valueaxis may be displayed in units of price, or a custom value designated bya user or pre-defined by the interface. Quantity information isrepresented in the interface through the display of a dimension of anorder icon. Precise information about each order is displayed either ina panel view or a pop-up window.”

U.S. Pat. No. 6,938,011 entitled “Click based trading with market depthdisplay,” that issued to Kemp et al. teaches “A method and system forreducing the time it takes for a trader to place a trade whenelectronically trading commodities on an exchange, thus increasing thelikelihood that the trader will have orders filled at desirable pricesand quantities. Click based trading, as described herein andspecifically the “Click” and “Dime” methods of the present invention,enables a trader to execute single mouse click trades for large volumesof commodities at a price within a pre-specified range.”

U.S. Pat. No. 6,772,132 entitled “Click based trading with intuitivegrid display of market depth,” that issued to Kemp et al. teaches “Amethod and system for reducing the time it takes for a trader to place atrade when electronically trading on an exchange, thus increasing thelikelihood that the trader will have orders filled at desirable pricesand quantities. The “Mercury” display and trading method of the presentinvention ensure fast and accurate execution of trades by displayingmarket depth on a vertical or horizontal plane, which fluctuateslogically up or down, left or right across the plane as the marketprices fluctuates. This allows the trader to trade quickly andefficiently.”

U.S. Pat. No. 6,766,304 entitled “Click based trading with intuitivegrid display of market depth,” that issued to Kemp et al. teaches “Amethod and system for reducing the time it takes for a trader to place atrade when electronically trading on an exchange, thus increasing thelikelihood that the trader will have orders filled at desirable pricesand quantities. The “Mercury” display and trading method of the presentinvention ensure fast and accurate execution of trades by displayingmarket depth on a vertical or horizontal plane, which fluctuateslogically up or down, left or right across the plane as the marketprices fluctuates. This allows the trader to trade quickly andefficiently.”

U.S. Pat. No. 6,408,282 entitled “System and method for conductingsecurities transactions over a computer network,” that issued to Buistteaches “The system and method of the preferred embodiment supportstrading of securities over the Internet both on national exchanges andoutside the national exchanges. The preferred embodiment supports animproved human interface and a continuous display of real-time stockquotes on the user's computer screen. The ergonomic graphical userinterface (GUI) of the preferred embodiment includes several functionalbenefits in comparison with existing on-line consumer trading systems.In the preferred embodiment, the users are subscribers to a securitiestrading service offered over the Internet. Preferably, each subscriberto this service is simultaneously connected from his own computer to afirst system which provides user-to-user trading capabilities and to asecond system which is a broker/dealer system of his/her choice. Thesystem providing the user-to-user trading services preferably includes aroot server and a hierarchical network of replicated servers supportingreplicated databases. The user-to-user system provides real-timecontinuously updated stock information and facilitates user-to-usertrades that have been approved by the broker/dealer systems with whichit interacts. Users of the preferred system can trade securities withother users of the system. As part of this user-to-user trading, a usercan accept a buy or sell offer at the terms offered or he can initiate acounteroffer and negotiate a trade.”

U.S. Pat. No. 5,297,031 entitled “Method and apparatus for ordermanagement by market brokers,” that issued to Gutterman et al. teaches“There is provided a broker workstation for managing orders in a marketfor trading commodities, securities, securities options, futurescontracts and futures options and other items including: a device forselectively displaying order information; a computer for receiving theorders and for controlling the displaying device; and a device forentering the orders into the computer; wherein the displaying devicecomprises a device for displaying selected order information about eachincoming order, a device for displaying a representation of an orderdeck and a device for displaying a total of market orders. In anotheraspect of the invention, there is provided in a workstation having acomputer, a device for entering order information into the computer anda device for displaying the order information entered, a method formanaging orders in a market for trading commodities, securities,securities options, futures contracts and futures options and the likecomprising the steps of: selectively displaying order informationincoming to the workstation; accepting or rejecting orders correspondingto the incoming order information displayed; displaying accepted orderinformation in a representation of a broker deck; and selectivelydisplaying a total of orders at the market price.”

Thus, it is desirable to solve some of the problems associated withimplementing trading strategies using electronic trading systems.

SUMMARY OF THE INVENTION

In accordance with preferred embodiments of the present invention, someof the problems associated with providing trading strategies forelectronic trading systems are overcome. A method and system forproviding automatic execution of black box trading strategies forelectronic trading is provided.

A black box trading entity is created from two or more real or synthetictrading entities including real or synthetic contracts or financialinstruments. The black box trading entity is automatically traded viaone or more electronic trading exchanges.

The foregoing and other features and advantages of preferred embodimentsof the present invention is more readily apparent from the followingdetailed description. The detailed description proceeds with referencesto the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the present invention are described withreference to the following drawings, wherein:

FIG. 1 is a block diagram illustrating an exemplary electronic tradingsystem;

FIG. 2 is a block diagram illustrating an exemplary electronic tradingdisplay system;

FIG. 3 is a flow diagram illustrating a method for displaying electronicinformation for electronic trading;

FIG. 4 is a block diagram of a screen shot of an exemplary tools window;

FIG. 5 is a block diagram of a screen shot of an exemplary settingswindow;

FIG. 6 is a block diagram of a screen shot of an exemplary quotes andcontracts window;

FIG. 7 is a block diagram of a screen shot of an exemplary order window;

FIG. 8 is a block diagram of a screen shot of an exemplary fill window;

FIG. 9 is a block diagram of a screen shot of an exemplary position andmarket data window;

FIG. 10 is a block diagram of a screen shot of an exemplary position andmarket data window for an order ticket from a sell position;

FIG. 11 is a block diagram of a screen shot of an exemplary position andmarket data window for a stop order;

FIG. 12 is a block diagram of a screen shot of an exemplary ABV window;

FIG. 13 is a block diagram of screen shot of an exemplary order ticketwindow;

FIG. 14 is a block diagram of a screen shot of an exemplary reportswindow;

FIG. 15 is a flow diagram illustrating a method for automaticallyexecuting a black box trading entity;

FIG. 16 is a flow diagram illustrating a method for automaticallycreating a black box trading entity; and

FIG. 17 is a block diagram illustrating creation of a black box tradingentity.

DETAILED DESCRIPTION OF THE INVENTION

Exemplary Electronic Trading System

FIG. 1 is a block diagram illustrating an exemplary electronic tradingsystem 10. The exemplary electronic information updating system 10includes, but is not limited to, one or more target devices 12, 14, 16(only three of which are illustrated). However, the present invention isnot limited to these target electronic devices and more, fewer or otherstypes of target electronic devices can also be used.

The target devices 12, 14, 16 are in communications with acommunications network 18. The communications includes, but is notlimited to, communications over a wire connected to the target networkdevices, wireless communications, and other types of communicationsusing one or more communications and/or networking protocols.

Plural server devices 20, 22, 24 (only three of which are illustrated)include one or more associated databases 20′, 22′, 24′. The pluralnetwork devices 20, 22, 24 are in communications with the one or moretarget devices 12, 14, 16 via the communications network 18. The pluralserver devices 20, 22, 24, include, but are not limited to, World WideWeb servers, Internet servers, file servers, other types of electronicinformation servers, and other types of server network devices (e.g.,edge servers, firewalls, routers, gateways, etc.).

The plural server devices 20, 22, 24 include, but are not limited to,servers used for electronic trading exchanges, servers for electronictrading brokers, servers for electronic trading information providers,etc.

The one or more target devices 12, 14, 16 may be replaced with othertypes of devices including, but not limited to, client terminals incommunications with one or more servers, or with personal digital/dataassistants (PDA), laptop computers, mobile computers, Internetappliances, two-way pagers, mobile phones, or other similar desktop,mobile or hand-held electronic devices. Other or equivalent devices canalso be used to practice the invention.

The communications network 18 includes, but is not limited to, theInternet, an intranet, a wired Local Area Network (LAN), a wireless LAN(WiLAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), aPublic Switched Telephone Network (PSTN) and other types ofcommunications networks 18.

The communications network 18 may include one or more gateways, routers,bridges, switches. As is known in the art, a gateway connects computernetworks using different network protocols and/or operating at differenttransmission capacities. A router receives transmitted messages andforwards them to their correct destinations over the most efficientavailable route. A bridge is a device that connects networks using thesame communications protocols so that information can be passed from onenetwork device to another. A switch is a device that filters andforwards packets between network segments. Switches typically operate atthe data link layer and sometimes the network layer therefore supportvirtually any packet protocol.

The communications network 18 may include one or more servers and one ormore web-sites accessible by users to send and receive informationuseable by the one or more computers 12. The one or more servers, mayalso include one or more associated databases for storing electronicinformation.

The communications network 18 includes, but is not limited to, datanetworks using the Transmission Control Protocol (TCP), User DatagramProtocol (UDP), Internet Protocol (IP) and other data protocols.

As is know in the art, TCP provides a connection-oriented, end-to-endreliable protocol designed to fit into a layered hierarchy of protocolswhich support multi-network applications. TCP provides for reliableinter-process communication between pairs of processes in networkdevices attached to distinct but interconnected networks. For moreinformation on TCP see Internet Engineering Task Force (ITEF) RequestFor Comments (RFC)-793, the contents of which are incorporated herein byreference.

As is known in the art, UDP provides a connectionless mode ofcommunications with datagrams in an interconnected set of computernetworks. UDP provides a transaction oriented datagram protocol, wheredelivery and duplicate packet protection are not guaranteed. For moreinformation on UDP see IETF RFC-768, the contents of which incorporatedherein by reference.

As is known in the art, IP is an addressing protocol designed to routetraffic within a network or between networks. IP is described in IETFRequest For Comments (RFC)-791, the contents of which are incorporatedherein by reference. However, more fewer or other protocols can also beused on the communications network 18 and the present invention is notlimited to TCP/UDP/IP.

Exemplary Electronic Trading Display System

FIG. 2 is a block diagram illustrating an exemplary electronic tradingdisplay system 26. The exemplary electronic trading system displaysystem includes, but is not limited to a target device (e.g., 12) with adisplay 28. The target device includes an application 30 that presents agraphical user interface (GUI) 32 on the display 28. The GUI 32 presentsa multi-window interface to a user.

In one embodiment of the invention, the application 30 is a softwareapplication. However, the present invention is not limited to thisembodiment and the application 30 can firmware, hardware or acombination thereof.

An operating environment for the devices of the electronic tradingsystem 10 and electronic trading display system 26 include a processingsystem with one or more high speed Central Processing Unit(s) (“CPU”),processors and one or more memories. In accordance with the practices ofpersons skilled in the art of computer programming, the presentinvention is described below with reference to acts and symbolicrepresentations of operations or instructions that are performed by theprocessing system, unless indicated otherwise. Such acts and operationsor instructions are referred to as being “computer-executed,”“CPU-executed,” or “processor-executed.”

It is appreciated that acts and symbolically represented operations orinstructions include the manipulation of electrical signals by the CPUor processor. An electrical system represents data bits which cause aresulting transformation or reduction of the electrical signals, and themaintenance of data bits at memory locations in a memory system tothereby reconfigure or otherwise alter the CPU's or processor'soperation, as well as other processing of signals. The memory locationswhere data bits are maintained are physical locations that haveparticular electrical, magnetic, optical, or organic propertiescorresponding to the data bits.

The data bits may also be maintained on a computer readable mediumincluding magnetic disks, optical disks, organic memory, and any othervolatile (e.g., Random Access Memory (“RAM”)) or non-volatile (e.g.,Read-Only Memory (“ROM”), flash memory, etc.) mass storage systemreadable by the CPU. The computer readable medium includes cooperatingor interconnected computer readable medium, which exist exclusively onthe processing system or can be distributed among multipleinterconnected processing systems that may be local or remote to theprocessing system.

Exemplary Method for Processing Electronic Information for ElectronicTrading

FIG. 3 is a flow diagram illustrating a Method 34 for processingelectronic information for electronic trading. At Step 36, one or moresets of electronic trading strategy information is obtained via one ormore windows on a application 30 on a target device 12, 14, 16 toautomatically execute one or more electronic trades on one or moreelectronic trading exchanges 20, 22. At Step 38, one or more sets ofelectronic trading information are continuously received on theapplication 30 via one or more application program interfaces (API),fixed or dynamic connections from one or more electronic tradingexchanges 20, 22. At Step 40, the one or more sets of electronic tradinginformation are displayed in one or more windows on the GUI 32 viaapplication 30. At Step 42, a test is conducted to determine if anyelectronic trades should be automatically executed based on the one ormore sets of electronic trading strategy information. If any electronictrades should be automatically executed, at Step 44, one or moreelectronic trades are automatically electronically executed viaapplication 30 an appropriate electronic trading exchange 20, 22. AtStep 45, results from any automatic execution of any electronic tradeare formatted and displayed in one more windows on a multi-windowedgraphical user interface (GUI) 32.

In one embodiment the one or more sets of electronic trading strategyincludes a pre-determined trading strategy created by a trader, if-thentrading strategies, one-cancels-other (OCO) trading strategies andelectronic trading strategies for synthetic instruments or syntheticcontracts, or execution of strategies based on previously executedorders.

As is known in the art, the pre-determined strategy trading strategy isa pre-determined trading strategy developed by a trader to apply to adesired market (e.g., cash, futures, stocks, bonds, options, spreadsetc.)

As is known in the art, a “synthetic” instrument or contract includes aninstrument or contract that does not really exist on any electronictrading exchange. A synthetic can be made up of one, or severalcontracts that trade on an exchange or multiple exchanges. For example,a synthetic contract may include automatically selling a call and buyinga put. Such a synthetic contract does not exist on any trading exchangebut is desirable to a selected group of traders.

As is known in the art, an API is set of routines used by an applicationprogram to direct the performance of actions by a target device. In thepresent invention, the application 30 is interfaced to one or more API.

In another embodiment, the application 30 is directly interfaced to afixed or dynamic connection to one or more electronic trading exchangeswithout using an API.

In one exemplary embodiment of the invention, the application 30interfaces with a Client API provided by Professional Automated TradingSystems (PATS) of London, England, or Trading Technologies, Inc. (TT) ofChicago, Ill. GL Multi-media of Paris, France and others. These APIs areintermediate APIs between the Application and other APIs provided byelectronic trading exchanges. However, the present invention is notlimited to such an embodiment and other APIs and other fixed or dynamicconnections can also be used to practice the invention.

The application 30 presents a user a multi-windowed GUI 32 thatimplements the functionality exposed through API provided by electronictrading exchanges. The application 30 allows the user to subscribe toand receive real-time market data. Additionally, the application 30allows the user to enter futures orders, cash orders, and other types offinancial products orders to all supported exchanges and receivereal-time order status updates. The application 30 supports at least twomethods of order entry; Order Ticket and Aggregated Book View (ABV).

The application 30 provides flexibility to the user to configure thedisplay of electronic information on the GUI 32. The application 30 andthe GUI are now described in further detail.

Desktop Layout Management

The application 30 provides the ability to manage Desktop Layouts. ADesktop Layout is a state of a GUI 32 as it appears to a user. Thisincludes, but is not limited to, number of windows, types of windows,and the individual window settings. A user is able maintain a list ofavailable Desktop Layouts. Each Desktop Layout has a unique name withinthe application 30. The user is able to create a new Desktop Layout andsave it, giving it a unique name. When the user saves a Desktop Layout,it is not saved in a minimized state but is instead saved in an expandedstate. The user is able to rename, copy, and delete a Desktop Layout.The user is able to load a saved desktop layout, replacing the currentlydisplayed configuration. The application 30 receives and loads desktoplayout templates from the communications network 18 upon user login. Theuser is able to export and import desktop layouts in order to port themfrom target device to target device. Desktop Layouts are saved on a userby user basis (e.g., by username). If two users access the application30 from the same target device 12, each user sees their own list oflayouts upon login.

The application 30 is launched from target device 12, 14, 16 or via thenetwork 18 (e.g., the Internet, an intranet, etc.) The application 30 isinstalled on a target device 12, 14, 16 or the communications network18. Upon startup, the application 30 detects if a new version isavailable. If the application 30 detects that an upgrade is warranted, awindow appears, asking the user if they would like to install the latestversion now. In one embodiment, if the user chooses not to install thelatest version upon startup, the current (older) version of theapplication 30 is launched. In another embodiment, another prompt isdisplayed when the user logs off. In the case of a critical update, theuser is not able to choose to run the application 30 without installingthe update.

The application 30 is pushed information that determines which serversthe application 30 is to connect to. IP addresses or Domain Name Servers(DNS) names are pushed to the client when upon login.

In one embodiment, the application 30 can be used by up to about 5,000simultaneous users. Scalability allows the application 30 to be used byup to about 20,000 simultaneous users. However, the present invention isnot limited to such an embodiment and other embodiments with othernumbers of simultaneous users can also be used to practice theinvention.

The application 30 indicates the status of a host connection 20, 22, 24on the communications network 18. As a minimum, “Connecting,”“Connected” and “Not Connected” statuses are indicated. The application30 indicates the status of an electronic trading exchange serverconnection 20, 22. As a minimum, “Connecting,” “Connected” and “NotConnected” statuses are indicated for the electronic trading exchangeserver connection.

If settings (e.g., accounts, contracts, etc.) change on a host system20, 22, 24, the application 30 updates the settings. The user does nothave to log back in to see the changes. The application 30 has theability to detect if any changes to accounts or contracts have beenmade. The application 30 is able to detect when a system administratorhas changed a network address (e.g., an Internet Protocol (IP) address,etc.) of the primary transaction server for a client.

The application 30 can log off of one network address and log ontoanother. Data integrity is maintained when a network address change hasbeen made. The application 30 notifies the user of any working orders oropen positions before closing. The user has the opportunity to cancelthe logout if they would like to cancel working orders or close the openpositions. The application 30 performs the normal logoff cycle whenclosed by the user. The application 30 saves all data needed to returnit to the state it was in when the application 30 was closed. Theapplication 30 saves all data necessary to restore it to the currentstate in the case of a catastrophic application 30 failure. If the userdoes not choose to download the most recent version of the application30 upon startup, a message appears upon logoff asking the user if theywould like to install the upgrade before closing.

The application 30 gracefully log users out at end of day. The userreceives a warning message, stating that the session is about to beclosed. The user needs to log back in to reestablish the connection. Theapplication 30 allows the user to combine the display of data ofdifferent types. Data types include, but are not limited to, Orders,Fills, Positions and Market Data. The application 30 supports thefunctionality exposed through the current version of a client API.

The application 30 supports data format differences between exchangesthat are not normalized by the client API. The application 30 supportsdifferences between exchange order handling semantics that are notnormalized by the client API. The application 30 gracefully handlesspreads. The application 30 support systems with multiple monitors. Allexchange contracts supported by a platform are considered by theapplication 30. Online user documentation is available to the user. Theapplication 30 runs on Windows 2000, Windows XP operating systems andother windowed operating systems (e.g., Linux, etc.). The application 30architecture is flexible in order to allow additional functionality tobe added when needed.

Standard Windows Grid

In a Standard Windows Grid, a user can select from a list of columns todisplay. The user is able to add or remove columns, but all columns maynot be able to be removed and certain columns may need to be added inorder to add other columns (if there are dependencies). Each window willhave certain columns that appear in the grid by default. The grid has acolumn heading with a caption (column name).

The user can change an order of the displayed columns by dragging thecolumn heading to a new position. The user can manually resize a column.The user can resize all columns to fit the screen. The user can resizeall columns to fit their contents. The user can resize a selected columnto fit the column's contents. This is accomplished by double clicking onthe column heading's right border. The user can change the foregroundand background colors of a column. The user can rename any grid column.The user can restore the default grid column names. The user can restoreall default grid settings.

The user can change the font for all columns in the grid. This includes,but is not limited to font type, color and size. The user can change thefont for an individual column. This includes, but is not limited to,font type, color and size. The user can sort the data in the grid byclicking on a column heading. The user can sort the data in ascending ordescending order. The user can create multiple sort criteria. The usercan create a filtered view of the information in a grid. The user canfilter on multiple criteria for non-numeric columns. Filters can includemore then one column. Multiple filters for numeric columns can becreated (e.g., for an =, ≠, <, >, ≦or ≧ operation, etc.). Thisfunctionality also allows the user to choose a range. The user canremove filters from a grid. Data in a grid will continue to be updatedwhile a filter is applied.

Login Window

A Login window will be launched via the application 30 when theapplication 30 is first accessed by the user. A user will enter a username and password in order to log into the application 30. A successfullogin will allow the user full access to multi-windowed GUI 32functionality. A failed login displays a message to the user, indicatingthat either the user name or password were invalid, but not which one.If Caps Lock is on, the failed login message the application 30indicates this fact. The failed login message reminds the user aboutcase sensitivity. The user is able to change passwords. The user doesnot have to be logged into the communications network 18 to changepasswords.

The application 30 updates a database with the new password. Allcharacters entered into a password field will be visible to the user asasterisks. A single login allows the user access to all supported andenabled exchanges.

Application Manager Window

An Application Manager Window allows the user to access all of thefunctionality of the application 30. It is via these windows that otherapplication windows are launched and managed. The GUI 32 windows areautomatically launched once the user has successfully logged in. Onlyone Application Manager window is launched by the application 30.

The Application Manager Window, by default, is a member of every displaylayout on the GUI 32 and cannot be removed. The user is able to view alist of available Desktop Layouts and select one to work with.

The user can create a new Tools window, Settings window, Contact andQuotes Window, Orders and/or Fills window, Positions/Market Data window,Aggregated Book View window, Order Ticket window and Reports window fromthe Application Manager Window. The user can also open a saved windowfrom the Application Manager Window.

The user can maintain Desktop Layouts from the Application ManagerWindow. The user can minimize all windows and restore all windows fromthe Application Manager Window.

Client Messaging Window

A Client Message Window allows the user to view system messages, tradingexchange messages and alerts. This window is automatically launched oncethe user has successfully logged in. In one embodiment, only one ClientMessaging window may be launched by the application 30. In anotherembodiment, more than one Client Message windows may be launched by theapplication 30. The Message display, by default, is a member of everydisplay layout and cannot be removed. Users who are logged on must beable to receive system messages, communications from office personnel,electronic trading exchange messages and alerts from various electronictrading exchanges 20, 22. Alert receipts are displayed for the user. Thewindow displays the entry and cancellation of orders (as messages).Alerts are given a priority, including, but not limited to, of“Critical,” “High,” “Medium” or “Low.”

Alerts of a high priority are presented in a more intrusive manner thanlower priority alerts. Upon login, users receive alerts from the currentday that were sent while they were logged off. The user is able to turnoff the display of alerts and are able to turn off the display ofmessages.

Tools Window

FIG. 4 is a block diagram of screen shot of an exemplary Tools window 46produced by application 30 and displayed on the GUI 32. The Tools window46 is used to launch other windows described herein on the GUI 32.

Settings Window

FIG. 4 is a block diagram of screen shot of an exemplary Settings window48 produced by application 30 and displayed on the GUI 32. The Settingswindow 48 allows the user to enter application-wide settings (such asdefaults, etc.) This window 48 is accessible via the Manager window. Thewindow 48 is different from any other window in the application.Multiple Settings windows cannot be opened, and this window is not partof a Desktop Layout.

The Settings window 48 displays network address (e.g., local andInternet IP addresses) of a target device 12, 14, 16. The Setting window48 displays the Host and Price server IP addresses and ports that arebeing used by the application 30.

In one embodiment, the user loads settings from a settings file via theSettings window 48. The settings file contains information necessary toreplicate the configuration of an application, including settings anddesktop layouts. For audible alerts, each alert should have a differentsound. The user can browse for sound files to assign to events. Inanother embodiment, settings are loaded from automatically from datastructure within the application 30.

The user can turn on or off audible and/or visual alerts for the eventslisted below in Table 1. However, the present invention is not limitedto these audible and/or visual alert events and more, fewer or othertypes of audible and/or visual alert events can be used to practice theinvention. TABLE 1 Logout Login Receipt of a fill Entry of an orderEntry of an order amend Entry of a cancel request Receipt of an orderReceipt of a cancel Receipt of an amend Receipt of a reject Receipt of amessage Order state timeouts Loss of connection to the host server Lossof connection to the price server Reconnection to the host serverReconnection to the price server Receipt of SARA alerts A differentsound/visual alert is used for each priority level. Limit breachContract breach Exchange disabled Stop price triggered for syntheticstops and stop limit orders Pull all orders End of day/End of market Byexchange This information is downloaded on login if an update is needed.Custom Reminders OCO fill OCO cancel Parked order violated If Then fillIf Then cancel P/L bracket fill P/L bracket cancel

The user can set the following defaults for an order ticket listed inTable 2. However, the present invention is not limited to these defaultsand more, fewer or other types of defaults can be used to practice theinvention. TABLE 2 Default Account Default Exchanges and ContractsDefault Order Type  The user can set the default order type by exchangeor to set the same default  for all exchanges. Default side DefaultQuantity  The user can set the default quantity by instrument or to setthe same default for  all instruments. Close after order entry  The usercan determine whether or not the Order Ticket should close by default after an order has been entered. Quantity set to zero after order entry The user can determine whether or not the order quantity should returnto zero  once an order has been placed. Default price for limit orders—Sell  The user can determine whether the price for sell limit ordersshould default to  current bid, ask, or last. Default price for limitorders —Buy  The user can determine whether the price for buy limitorders should default to  current bid, ask, or last. Other SettingsAlways on Top  The user can set which window should stay on top bydefault (if any).  This default may be overridden on a window by windowbasis. Order State Timeouts  The user can set the amount of time that anorder can remain in a state of Sent,  Queued, Cancel Pending or AmendPending before an order state timeout alert  is generated. CustomReminders  The user can create and maintain a list of custom reminders,which will create an audible  and visual alert at the set date and time. The user can assign a title, date, time and description to eachreminder.  Custom reminders are saved on the local machine. ABV MarketDepth  The user can set the amount of market depth displayed on the ABVwindow.  A Market Depth setting greater than the maximum depthdisseminated by the  exchange will be treated as the exchange maximum.Hot Keys  The user can assign program shortcuts to keyboard functionkeys. Fonts  The user can set a default font for all text on allwindows.  The user can restore all fonts to the font selected here(after changes have been  made on individual windows). Key Pad (forQuantity)  The user can assign the values for keypad buttons.  Thesevalues will be displayed on the key. Order Quantity Limits (Fat FingerRules)  The user can set the maximum quantity that may be entered for anorder.  An order exceeding this limit will not be entered. Commissions The user can enter commission amounts by exchange and/or by instrument. The commissions set here are used in the user's P&L calculations. PrintReports  The user can choose whether or not a window should appear uponlogoff, asking  if reports should be printed.  From the window (ifdisplayed), the user should be able to specify which reports  areprinted.Contracts and Quotes Window

FIG. 6 is a block diagram of screen shot of an exemplary Quotes andContracts window 50 produced by application 30 and displayed on the GUI32. The user can select which exchange 52 (e.g., Chicago MercantileExchange (CME), Chicago Board of Trade (CBOT), New York Stock Exchange,etc.) and which instruments, contract and contract date combinations(e.g., Mini NSDQ March 2005) to display 54. Market data associated witha position by the unique instrument information is also displayed.

Order and Fills Windows

The user is able to display any combination of order and fillinformation that they choose (although some information must bedisplayed in order for other information to be displayed) in Order andFill windows respectively. The user is provided with an Orders templateand a Fills template, which will each display different default data(and, therefore, provide different functionality based on user definedpreferences set via the Settings window 48).

FIG. 7 is a block diagram of screen shot of an exemplary Order window 56produced by application 30 displayed on GUI 32. Typically, an order iscreated by the user and submitted to an electronic trading exchange 20,22 for possible execution. One exception to this is the Parked order. Inthis case, the application 30 saves the order until it is released bythe user to the electronic trading exchange 20, 22.

In one embodiment, the Order window 56 displays, but is not limited to,a controls identifier, a state identifier (e.g., rejected, working,filled, held) an account identifier (e.g., APIDEV5), an order number, aninstrument identifier (e.g., CME\MINI S&P), a side designationidentifier (e.g., buy or sell), a quantity, a price, a type identifier(e.g., limit, pre-defined stop price, market price) an average price.However, the present invention is not limited to displaying these itemsand more, fewer or other items can be displayed in the Order window 56to practice the invention.

FIG. 8 is a block diagram of screen shot of an exemplary Fills window 58produced by application 30 displayed on GUI 32. Typically, a fill is anacknowledgment from an electronic trading exchange 20, 22 where theorder was submitted that all or part of the order was executed. Aspecial case is an external fill. An external fill is submitted manuallyby a system administrator.

In one embodiment, the Fills window 58 displays, but is not limited to,a control identifier, an order identifier, an instrument identifier, aside identifier, a fill quantity, a fill identifier and a fill price.However, the present invention is not limited to displaying these itemsand more, fewer or other items can be displayed in the Fills window 58to practice the invention.

A new or saved Order and Fill windows 56, 58 can be launched from theApplication Manager window. When the user creates and submits an orderto an electronic trading exchange 20, 22, an order with a quantitygreater then the maximum order limit will be rejected by the application30. The user can create a trailing stop order against a filled order.The user is also able to create a Profit/Loss bracket around a filledorder.

The user can also create a “Parked” order. A Parked order is an orderthat is created by the user but not submitted to an electronic tradingexchange 20, 22. Parked orders are saved by the application 30 and madeavailable to the user between application 30 launches. The user canchange a working order to a parked order and visa versa. Changing aworking order to a parked order, the application 30 sends a cancel tothe selected electronic trading exchange 20, 22. On receipt of thecancel acknowledgement, the application 30 will change the order stateto indicate that the order is parked.

The user can also submit a Parked order to an electronic tradingexchange 30. The user can submit all parked orders at once. The user canselect certain parked orders to submit (at once). The user can changethe electronic trading exchange and/or contract for a parked order. Ifthe user changes the contract, the application 30 will verify that theentered price is valid for the new contract. If the entered price isinvalid for the new contract, the application 30 will prompt the user tochange the price. The user can change the account for a parked order.

The user can cancel a working order. In one embodiment, a working ordercan be canceled with a single mouse click. In another embodiment aworking order can be canceled with two mouse click, one to cancel theorder and one to confirm cancellation. The user can cancel all workingorders in a selected account, cancel all working buy orders in theselected account, all working sell orders in the selected account.

The user can delete a parked order. The use can delete a parked orderwith a single mouse click. The user can delete all parked orders in aselected account. The user can delete all parked orders in all accounts.

The user can change the following order information (for a workingorder) illustrated in Table 3. However, the present invention is notlimited to this order information and more, fewer or other types oforder information can be used to practice the invention. TABLE 3 Prices(stop/limit/stop limit) Quantity  The user must be able to display thedetailed order history  for an order (both parked orders and thosesubmitted  to an exchange. The order history includes orders that led tothe current order if the order was created by a cancel/replace or aparked order.

The user can also create a trailing stop order against a fill. The usercan create a Profit/Loss bracket around a fill. The user can launch anOrder Ticket window from a specific fill. When an Order Ticket is openedfrom a fill, the ticket is pre-populated with the data that correspondsto that fill (e.g., exchange, instrument, quantity, etc.)/The side ofthe Order Ticket will be opposite that of the fill. Supported ordertypes will be available to be created from the Order Ticket. Trailingstops and brackets can be linked to another order, such as a limitorder. When this order is executed the Trailing Stop or bracket, etc. isthen submitted to the market, or held “working” on the target device 12,14, 16.

The Fills window 58 displays a detailed view of a fill. A fill detailincludes all available fill information (including partial fills). Theapplication 30 handles external fills. The application 30 uses separatedisplay indicators if the fill is external (e.g., color difference, etc)on the GUI 32.

In one embodiment, Order and Fill information is displayed followingstandard window rules laid out by the Standard Window. The data in thisOrder and Fill window is displayed in the standard grid format, asdescribed in the Standard Grid. This window will display order and filldata. The user chooses which fields should be displayed in the grid(some fields will appear by default) on the GUI 32.

Table 4 illustrates a list of order information that used in the Orderand Fill windows 56, 58. Most of the information is exposed through theAPIs used. However, in a few cases the information is calculated. Theseexceptions are indicated where they occur. However, the presentinvention is not limited to this order information and more, fewer orother types of order information can be used to practice the invention.TABLE 4 Order ID Display ID Exchange Order ID User Name Trader AccountOrder Type Exchange Name Contract Name Contract Date Buy or Sell PricePrice2 Lots Linked Order Amount Filled Number of Fills Amount Open  Thisfield is calculated by the application 30 using contract lots minus amount filled. Average Price  This field (the average price of allfills that make up an order) is calculated by the application 30 becausethe API does not return the correct value if there is only one lot.Status Date Sent Time Sent Date Host Received  This field will notdisplayed to the user, but is used for logging. Time Host Received  Thisfield will not be displayed to the user, but is used for logging DateExchange Received  This field will not be displayed to the user, but isused for logging. Time Exchange Received Date Exchange Acknowledged TimeExchange Acknowledged Non Execution Reason Good-Till-Date

Table 5 illustrates a list of fill information that used in the Orderand Fill windows 56, 58. Most of the information is exposed through theAPIs used. However, in a few cases the information is calculated. Theseexceptions are indicated where they occur. However, the presentinvention is not limited to fill information and more, fewer or othertypes of fill information can be used to practice the invention. TABLE 5Display ID Exchange Order ID User Name Trader Account Order TypeExchange Name Contract Name Contract Date Buy or Sell Lots Price AveragePrice  This field will need to be calculated by the application becausethe  API does not return the correct value if there is only one lot.Date Filled Time Filled Date Host Received  This field will never bedisplayed to the user, but is used for logging. Time Host Received  Thisfield will never be displayed to the user, but is used for logging FillType Fill, External, Netted, RetainedPositions/Market Data Window

FIG. 9 is a block diagram of screen shot of an exemplary GUI 32 Positionand Market Data window 60 produced by application 30 displayed on theGUI 32. The Positions and Market Data Window 60 provides representationand display of open positions and market data in the application 30.

In one embodiment, the Positions and Market Data window 60 includes, butis not limited to a display of a controls identifier, an accountidentifier, a net position, a number of buys, a number of sells, anaverage price, an last price and a total. However, the present inventionis not limited to displaying these items and more, fewer or other itemscan be displayed in the Position and Market Data window 58 to practicethe invention.

The user can display any combination of order and fill information thatthey choose (although some information must be displayed in order forother information to be displayed). The user is provided with an Orderstemplate and a Fills template, which will each display different defaultdata (and, therefore, functionality).

An “open position” is a long, short, or profit or loss in an instrumentor contract in an account. This open position is the aggregation of allthe fills received in the instrument. Market data is delivered to theapplication 30 in real-time through the APIs used. A new or savedPositions/Market window 60 can be launched from the Application Managerwindow. The user can launch an Order Ticket window 84 from a specificposition.

FIG. 10 is a block diagram of screen shot of an exemplary Position andMarket Data window for an Order Ticket from a sell position 62 producedby application 30 and displayed on the GUI 32. When a ticket is openedfrom a position, an Order Ticket window 84 is pre-populated with thedata that corresponds to that position (e.g., exchange, instrument,quantity, etc.). For example in FIG. 10, an Order Ticket window includesdata (e.g., APIDEV5, CME\MINI S&P, Limit, Limit Px 4.45, Quantity 2,etc.). The side of the Order Ticket will be opposite that of theposition. The user can launch a window that will allow them to create aProfit/Loss (P/L) Bracket around an open position. The order sidesdefault to opposite of the position. The order quantities default to theposition quantity. The user can also launch a window that will allowthem to create a Stop or Stop Limit order against an open position.

FIG. 11 is a block diagram of screen shot of an exemplary Position andMarket Data window for a sell stop order 64 produced by application 30displayed on the GUI 32. The order side defaults to opposite of theposition. The order quantity defaults to the position quantity. The usercan also launch a window that will allow them to create a Limit orderagainst an open position. The order side defaults to opposite of theposition. The order quantity defaults to the position quantity.

The user can display all of the fills that comprise a position. The usercan flatten the open position in the instrument for the selectedaccount. The window 60 includes a Flatten button for flattening a netposition. When the user chooses to flatten, working orders for theinstrument are canceled and an order is entered that flattens the netposition (i.e., the quantity of the order will be equal to the netposition and the order will be placed on the opposite side of the netposition). The flattening is achieved with a single order (i.e., theuser cannot enter more than one order to flatten).

Position information and Market Data is displayed following standardwindow rules laid out in the Standard Window. The data in this window 60is displayed in the standard grid format, as described in the StandardGrid.

Table 6 illustrates a list of position information that is availablefrom this window 60. However, the present invention is not limited tothis position information and more, fewer or other types of positioninformation can be used to practice the invention. TABLE 6 AccountExchange Name Contract Name Contract Date Net Position Avg. Price OpenP&L Cumulative P&L Total P&L Commission

The GUI 32 will also show market data and position information. The userchooses which fields should be displayed in the grid (i.e., some marketdata fields will appear by default). Table 7 is a list of market datathat is available from this window 60. However, the present invention isnot limited to this market data more, fewer or other types of marketdata can be used to practice the invention. TABLE 7 Exchange NameContract Name Contract Date Bid Price Bid Size Ask Price Ask Size LastTraded Volume Net Price Change Last Traded Price High Price Low PriceOpening Price Closing Price Total Traded Volume Contract Status  This isthe status of the contract on the exchange (i.e. open, pre-open, trading, etc.)Aggregated Book View (ABV) Window

The ABV Window allows the user to view bid size and offer size by pricefor a particular instrument in a market depth-type format. The windowdisplays working orders for a selected account in a single instrument.The data on this window is displayed and updated in real-time. Thewindow also allows the user to enter various order types. In oneembodiment, two ABV widows are displayed by default. In anotherembodiment, one or more than two ABV windows are displayed by default.

FIG. 12 is a block diagram of screen shot of an exemplary ABV window 66produced by application 30 displayed on GUI 32. The ABV window 66includes a dynamically displayed Price column 68.

In one embodiment, the ABV window displays a buy column, a bid column, adynamic price column, an ask column, a sell column, a quantity column, are-center button, a cancel buy button, a cancel sell button, a cancelall button, a market buy button, a flatten button, a bracket button, aTStop button, a net position and a total P/L. However, the presentinvention is not limited to displaying these items and more, fewer orother items can be displayed in the ABV window 66 to practice theinvention.

The user can select an instrument or contract to view in an ABV window66, and can change the instrument or contract from this window 66.Changing the instrument or contract changes the data displayed to thatof the selected instrument or contract. The user can select an accountfrom available accounts. The window 66 displays the total quantity oforders working in the market at each price. Both buy and sell quantitiesare displayed. Quantities are updated as the instrument order bookchanges. The window 66 displays an indicator depicting the all of theuser's open orders, for the selected account, at each price. The window66 indicates a state of each order. Open order states include, but arenot limited to: Queued, Sent, Working, Part Filled, Cancel Pending andAmend Pending, Held, Cancelled, Filled.

This window 66 indicates the order type for each order. The window 66indicates the working quantity of each order. The window 66 displaysparked orders for the selected instrument. The window 66 displays theuser's net position in the selected instrument for the selected account.The window 66 displays the trade quantities for each corresponding pricelevel. The user can select to view the total quantity currently tradingat a price. This quantity is increased as each trade at a price occurs.The cumulative quantity remains in the window 66 until the price changes(at which time the cumulative trade quantity for the new price will beshown).

The user selects to view the last quantity currently trading at a price.This view shows the individual trade quantities. Only quantities for thecurrent price are shown. The window 66 displays the total traded volumefor the instrument. The window 66 displays all of the aforementioneddata at once.

The user sets and adjusts the specified quantity for orders entered viathis window 66. The quantity is set via a spinner, text entry or keypadentry. Each key-pad input increases a specified quantity by an amountdisplayed on the key (key value). The user selects to have the specifiedquantity set to zero after order entry. The user resets the quantity tozero (i.e., without entering an order). A right click on the mouseincreases the quantity, left click decreases the quantity.

Orders entered via this window 66 will have a quantity equal to thequantity specified at time of entry. The default account for any ordersentered from the ABV window 66 is the selected account. The can enter alimit order by clicking a cell in the bid quantity or offer quantitycolumns. Limit orders are default order type.

Order side will be set to BUY if the user clicks in the bid quantitycolumn 70. Order side will be set to SELL if the user clicks in theoffer quantity column 72. Orders will have a quantity equal to thespecified quantity. Order limit price must equal the price correspondingto the clicked offer/bid quantity.

The user enters a stop order by clicking a cell in the bid or offerquantity columns 70, 72. Order side will be set to BUY if the userclicks in the bid quantity column 70. Order side will be set to SELL ifthe user clicks in the offer quantity column 72. Orders must have aquantity equal to the specified quantity. The order stop price willequal the price corresponding to the clicked offer/bid quantity. Theorder is entered for the selected account. The user is able to enter abuy stop below the market or a sell stop above the market. If the userdoes this, a window appears, warning the user that the buy or sell willbe immediately executed.

The user can enter an OCO (One Cancels Other) pair of orders. The usercan also enter a profit/loss bracket. The user can enter a trailingstop. The user can also enter an “If-Then Strategy.”

The user can change the limit price of a working limit order by draggingthe working order indicator to a new price. The user can change the stopprice of a working stop order by dragging the working order indicator toa new price. This will cause a cancel replace to be entered at theelectronic trading exchange 20, 22. The user can change the quantity ofa working order by right clicking in the cell displaying the workingorder. A right click on a mouse displays a context menu listing orderquantities centered on the current quantity. The user can also adjustaccount number.

The user can cancel a working order with a single mouse click. The usercan cancel all open orders in the instrument for the selected account.The can cancel all open buy orders in the instrument for the selectedaccount. The user can cancel all open sell orders in the instrument forthe selected account.

Users can have orders at a price displayed as a concatenated total, ordisplayed as each individual order. When the display of individualorders is to large for the display, individual orders will be displayedstarting with the first order entered and then the remaining orders thatdo not fit in the display will be concatenated. Concatenated orders areindicated as such using a symbol that is attached to the total. Userscan also adjust the display of the ABV by adding or removing columns,buttons and functions.

The user uses the open position in the instrument for the selectedaccount. This window 66 includes a Flatten button for flattening the netposition. When the user chooses to flatten, all working orders for theinstrument are canceled and an order is entered that flattens the netposition (i.e., the quantity of the order will be equal to the netposition and the order will be placed on the opposite side of the netposition). The flattening is achieved with a single order (i.e., theuser cannot enter more than one order to flatten).

The user can center the dynamic Price column 68 on the current market.The user can scroll the dynamic Price column 68 to display prices aboveor below the current market. All data is displayed real-time.

This ABV window 66 follows the standard window rules laid out in theStandard Window. The data in this window is displayed in a grid, butthis grid will not follow all of the standard grid rules.

The user can choose from a list of columns to display. Certain columnswill be displayed by default. Certain columns will not be removable(price for example). The user can change the order of the displayedcolumns by dragging a column heading to a new position. The user canmanually resize a column. The user can resize all columns to fit thescreen. The user can resize all columns to fit the contents. The usercan resize a selected column to fit the contents. Double clicking on thecolumn heading border sizes a column so that data only is displayed withno redundant space.

The user can change the font for all columns in the grid. The user canchange the font for an individual column. The user can change theforeground color of a column. The user can change the background colorof a column. The user can restore the default grid settings.

The ABV window 66 is resizable. When it is resized, the columns expandand contract so that all data is still shown. However, after resizingthe window, the user can resize the columns to get rid of wasted spaceand then change the font size (i.e., so it's more readable when thescreen is small).

This ABV window 66 will display the following fields illustrated inTable 8 in a ladder format. However, the present invention is notlimited there fields and more, fewer or other types of fields can beused to practice the invention. TABLE 8 Price  Centered on the currentmarket prices when launched. Market Bid Quantity Market Offer QuantityTrade Quantity as determined in section 11.3 above Open Buy Ordersindicating status, type and quantity for each order Open Sell Ordersindicating status, type and quantity for each order Parked Orders

The ABV window 66 displays real-time data for a particular contract,allowing a user to get a current snapshot of the market. Thus, the ABVwindow 66 can also be considered an “Ask, Bid, Volume” window.

An instrument or contract can be added to an open ABV window 66 in thesame way that a contract was added to the Quotes window 50. Simplyselect the contract that to display and then drag it into the ABV window66. Contracts can be dragged from any of the windows displayed on thescreen.

Once a contract has been added to the ABV window, the data illustratedin Table 9 is displayed on the ABV window. TABLE 9 A current number ofBids 70 and Asks 72 on an electronic trading exchange 20, 22 forparticular price levels. A total quantity currently trading at a certainprice. A number in parentheses 74 next to the total quantity is the lastquantity traded at that price. A price in red is the daily high 76. Aprice shown in blue is the daily low 78. A last traded price is shown ingray 80. The last traded price 82 is also highlighted on a dynamic pricecolumn 68. When there has been an uptick in this price, this cell willbe green. When there has been a downtick, this cell will be red. Ifthere has been no change, this cell will appear yellow. The Buy and Sellcolumns display a total number of open orders at each particular price.For example, a “W2” in the Buy column indicates that there are workingorders with a total quantity of two at the specified price. Net Positionand Total P/L on the ABV can be monitored by simply referring to thelower right hand corner of the window.

On the ABV window 66, the price of any open Buy or Sell orders can beamended. To change the price of an order, a row selector thatcorresponds with the order to amend is selected buy left-clicking andholding down a left mouse button, dragging a cursor connected to themouse up or down to a desired new price and releasing the mouse button.A white cursor arrow appears to indicate a change in price. The priceamended will be submitted as soon as the mouse is released. If theremultiple orders at the same price (and on the same side), all of theorders will be amended to the new price when dragging the concatenatedorder. The user can cancel a signal order at a price where multipleorders exist. They can also modify a single order at a price wheremultiple orders exist. They do this by selecting the individual orderand dragging and dropping.

Another feature of the ABV window 66 is that a desired position on thedynamically displayed Price column 68 can be moved. If it is desired toscroll up or down on a market price on the dynamically displayed Pricecolumn 68, the dynamically displayed Price column 66 is hovered overwith a mouse. A yellow cursor arrow will appear, pointing up if themouse cursor is in the top half of the dynamic price column 68, or down,if the mouse cursor is in the bottom half of the dynamic Price column68. Clicking on the cursor arrow will scroll the grid in the directionthat the arrow points.

The ABV window 66 provides a dynamic Price column 68 centered upon thelasted traded price that continuously changes with fluctuations in thelast traded price. To enter an order, a mouse cursor is hovered anywherein the ABV window 66. This mouse hover puts a user in the “order entrymode.” In the order entry mode a trade near last traded price can beentered or prices on the dynamic price column can be manually adjustedaway from the last traded price. To scroll up or down the market priceson the dynamic Price column 68 to enter a trade, the mouse cursor ishovered over the dynamic Price column 68. A large yellow arrow willappear, pointing up if the mouse curser is in the top half of thedynamic price column, or down, the mouse cursor is in the bottom half ofthe dynamic price column. Clicking on the large yellow arrow will scrollthe prices in the dynamic price column in the direction that the largearrow points so a trade can be entered away from a current market price.

If the dynamic Price column 68 is scrolled up or down and the lasttraded price is not centered on your ABV, the dynamic price column willstart to scroll until the last traded price is again centered in the ABVwindow 66. In addition, if there is no further activity from a mouse fora period of time the dynamic Price column 68 will also start to scroll.As a visual indication, just before the dynamic price column begins toscroll, the mouse cursor will turn yellow and start to flash. This is awarning that the ABV window is about to begin re-centering around thelast traded price. If, at any time, the mouse cursor is moved out of theABV window, you leave the order entry mode and the ABV willautomatically re-center the dynamic price column on the last tradedprice the next time the market price changes.

Stop and limit orders can also be entered on the ABV window 66 with justa click of a mouse. Before entering limit or stop orders an account ischosen and a quantity is entered. If a user has access to multipleaccounts, the user can select the desired account by using the Accountdrop down menu. The user can input a number of lots to trade by typingthe number in, by using the + or − buttons, or by using a keypad. Adefault quantity can be set via the Settings window. After selecting anaccount and quantity, limit and stop orders can be placed.

To enter a Buy Limit order, the mouse is clicked in the Bid column nextto the Price to enter the order for. A limit order to buy will beentered at that price for the quantity specified, and a new workingorder will be reflected in the Buy column. Likewise, to enter a SellLimit order, the mouse is clicked in the Ask column next to the Price toenter the order for.

To enter a Buy Stop order, the mouse is right-clicked in the Bid columnnext to the Price to enter the order for. A stop order to buy will beentered at that price for the quantity specified, and a new order willbe reflected in the Buy column. Similarly, to enter a Sell Stop order,the mouse is right-clicked in the Ask column next to the Price that youwant to enter the order for.

In addition to Limit and Stop orders, Market orders can be executed onthe ABV window 66 using the Market Buy and Market Sell buttons. The ABVwindow can also be set up so that a Bracket or Trailing Stop order willautomatically be created any time an order entered via the ABV isfilled. The Bracket and Trailing Stop parameters will default to thevalues set up on the Settings window. To link a Bracket or Trailing Stoporder to all orders entered via the ABV, choose Bracket or TStop fromthe Link To drop down box. A small window pops up with the defaultparameters for a bracket. The bracket levels can be changed by typing ina desired number, or using the “+” and “−” buttons. A limit order willbe the profit order type, and for a loss order type, either choose astop or a trailing stop can be selected.

For example, if a stop order is chosen, as soon as the order was filled,two new orders were entered. A limit order was created at a price thatis five ticks above the market order's price and a stop order wascreated at a price that is three ticks below the market order's priceBoth orders have the same quantity that the market order had. Becausethese orders were entered as part of a bracket, when one of these ordersis filled, the other will automatically be cancelled. Likewise, TStop ischosen from the Link To drop down box, a small window will appear thatallows you to view and change trailing stop parameters. Like thebracket, a trailing stop will be entered once an order entered via theABV window 66 is filled.

The ABV also allows cancellation of some or all of working orders aswell. To cancel a particular order, the mouse cursor is placed over thatorder in the Buy or Sell column, whichever applies, and a yellow Xappears over the working order. A mouse click on the yellow X willcancel that particular order. If multiple orders are entered at the sameprice (and on the same side), they will all be cancelled.

Order Ticket Window

FIG. 13 is a block diagram of screen shot of an exemplary Order Ticketwindow 84 produced by application 30 and displayed on GUI 32. Thiswindow 84 allows the user to create and enter all types of orderssupported by the application and the APIs used. This window 84 isaccessible via all windows except for Login, Settings, Client Messagingand Reports windows. Multiple order tickets can be launched and multiplewindows 84 will be created. The Order Ticket window 84 is a member of aDesktop Layout. Order types, including Synthetic order types can beentered from this window.

In one embodiment, the Order Ticket window 84 displays, but is notlimited to, an account identifier, an instrument or contract identifier,an order type, a limit price, if any, a stop limit price if any, a sideidentifier, a quantity identifier, an exchange identifier a current bid,ask, and last traded price, a current bid, ask or last traded quantityand a buy or sell identifier. However, the present invention is notlimited to displaying these items and more, fewer or other items can bedisplayed in the Order Ticket window 84 to practice the invention.

If necessary, the Order Ticket window 84 will change or launchsupporting windows to accommodate more complex order types. In oneembodiment, the Order Ticket window 84 displays, but is not limited to,an account identifier, an instrument or contract identifier, an ordertype, a limit price, if any, a stop limit price if any, a sideidentifier, a quantity identifier, an exchange identifier a current bid,ask, and last traded price, a current bid, ask or last traded quantityand a buy or sell graphical button. However, the present invention isnot limited to this embodiment and other embodiments can be used topractice the invention.

The user can select the account that the order applies to. The user canchange the side of the order. The ticket background color depends uponthe side chosen. For example, the background is set to blue for buyorders and set to red for sell orders. The following market data isdisplayed, but is not limited to, on this window 84 for the selectedinstrument: bid price, bid size, ask price, ask size, and last tradedprice.

This window 84 also does follow the standard window rules laid out inthe Standard Window. The window can also be resized. The user can selectto have the order ticket always on top. The default for thisfunctionality is determined in the Settings Window. The Order Ticketwindow 84 is member of a Desktop Layout window. The Order Ticket window84 settings are saved when it is a member of a Desktop Layout.

This window 84 is comprised of all the fields necessary to enter anorder. The field defaults are set in the Settings window 48, but thiswindow 84 may display different defaults depending on where it waslaunched from (for example, if it was launched from a specific fill orposition).

Table 10 illustrate a list of the fields that are used to create astandard order. Synthetic orders also created directly from this window84. In another embodiment, a separate window may be launched, or theremay be some other method of accessing synthetic order entry. However,the present invention is not limited to this order information and more,fewer or other types of order information can be used to practice theinvention. TABLE 10 Exchange  The default value for this field isdetermined from the window where it was  launched or in Settings.Instrument  This field is filtered to display valid instruments based onthe exchange that is  selected. Contract Date  This field is filtered todisplay valid contract dates based on the instrument that is  selected.Order Type  This field is filtered to display valid order types based onthe exchange that is  selected. Limit Price  This field defaults toeither the current bid, ask or last as determined by Settings and  bythe side.  This price does not change once the order is open.  Thisfield is enabled only for stop, stop limit, MIT orders and the synthetic equivalents for those order types.  The use is able to enter the pricevia keyboard entry or spinner, Order Quantity  The user is able tochange the specified order quantity through a key-pad control.  Eachkey-pad input increases the specified quantity by the amount displayedon  the key (the key value).  The user has ability to set the quantityback to zero.  The user is able to select to have the specified quantityset to zero after order  entry. Secondary Price  This field is enabledonly for stop limit orders. Good-Till-Date  This field is enabled onlyfor orders with TIF (Time in Force) of GTD.  This field defaults to thecurrent trade date.Reports Window

FIG. 14 is a block diagram of screen shot of an exemplary Reports window86 produced by application 30 displayed by GUI 32. The Reports window 86allows the user to create and enter all types of orders supported by theapplication 30 and APIs used. This window is accessible via all windowsexcept for Login, Settings, Client Messaging and Reports. Multiple ordertickets can be launched. The order ticket can be a member of a DesktopLayout window.

In one embodiment, the Reports window 86 displays, but is not limitedto, an account identifier, an order identifier, an instrumentidentifier, a side identifier, a quantity, a price, an order type, anaverage price, a state, a price 2, file, number of fills and an opencolumn. However, the present invention is not limited to displayingthese items and more, fewer or other items can be displayed in theReports window 68 to practice the invention.

Order types, including synthetic order types are summarized from thiswindow 86. If necessary, the Order Ticket window 84 changes or launchessupporting windows to accommodate more complex order types. The user canselect the account that the order applies to. The user changes the sideof the order. Ticket background color depends upon the side chosen. Forexample, the background is blue for buy orders ant he background is redfor sell orders.

Table 11 illustrates a list of the fields used to create a standardorder report. However, the present invention is not limited to thisorder information more, fewer or other types of order information can beused to practice the invention. TABLE 11 Exchange   The default valuefor this field is determined from the window where it was   launched orin Settings. Instrument   This field is filtered to display validinstruments based on the exchange that is   selected. Contract Date  This field is filtered to display valid contract dates based on theinstrument that is   selected. Order Type   This field is filtered todisplay valid order types based on the exchange that is   selected.Limit Price   This field defaults to either the current bid, ask or lastas determined by Settings   and by the side.   This price does notchange once the order is open.   This field is enabled only for stop,stop limit, MIT orders and the synthetic   equivalents for those ordertypes.   The user is able to enter the price via keyboard entry orspinner. Order Quantity   The user is able to change the specified orderquantity through a key-pad control.   Each key-pad input increases thespecified quantity by the amount displayed on   the key (the key value).  The user has ability to set the quantity back to zero.   The user isable to select to have the specified quantity set to zero after order  entry. Secondary Price   This field is enabled only for stop limitorders. Good-Till-Date   This field is enabled only for orders with TIF(Time in Force) of GTD.   This field defaults to the current trade date.  This window allows the user to view and print reports. Screen Access  This window is accessed via the Manager window. Multiple reportwindows   cannot be launched. The report window is not a member of anyDesktop Layout. Functional Requirements   No trading functionality isavailable from this window. Fill Report   The user is able to view andprint a fill report by account for the current day.   The data for thisreport is saved on the client. Order History Report   The user is ableto view and print an order history report for the current day or for  any range of time up to 30 days. History includes parked orders.   Thedata for this report should is on the client machine 30. Orders EnteredReport   The user is able to view a report showing orders entered thatwere filled for the   current day or for any range of time up to 30days.   The data for this report is saved on the client.Client Logs

This functionality allows the user to send error and audit logs. A logof application errors is maintained. Application error logs, createddaily, are retained for ten trading days. The user does not have abilityto view the application error log. Logs are stored on the client and arenot be encrypted, but should not be easily accessible to the user. Theuser can send the application error log to another location from withinthe application 30.

An audit log is created. The audit log contains detailed order history,including all available times associated with the order. The log alsocontains fills associated with the order. The log contains messagespertaining to the application which indicate connection activities andstatuses. Audit logs, created daily, are retained for ten trading days.The user does not have ability to view the audit log. Logs are stored onthe application 30 and should not be encrypted, but should not be easilyaccessible to the user. The user can send the audit log to anotherlocation from within the network 18.

Specialized Order Functionality

The application 30 also provides specialized order functionality. Thisfunctionality is available to the user wherever orders can be entered.The user creates one-cancels-other (OCO) order pairs. An OCO order isone that allows the user to have two working orders in the market atonce With the execution of one order the other is canceled. The user canconstruct an OCO pair across different instruments traded on a singleelectronic exchange. The user can construct an OCO pair across differentinstruments on two electronic trading exchanges. The user can constructan OCO pair combining orders of any order type that is supported by theexchange (or supported synthetic order types).

The user cancels OCO orders before exiting the application 30. If theuser has any open OCO's upon logoff, the GUI 32 warns the user that theorders will be cancelled and allow the user to cancel the logoff ifdesired. By default, entering a quantity for the OCO enters that samequantity for both sides of the OCO.

A complete fill of one order cancels the other order. If there is apartial fill on one leg of the OCO, the other side of the OCO is reducedby the amount that was filled. This functionality will only occur ifboth legs of the OCO are entered with the same quantity. The user hasthe ability to turn off this functionality, so that the order quantitiesdon't automatically decrement and the orders are canceled only when oneorder is completely filled. If the user enters different quantities,this functionality are automatically turned off and disabled.

The user can cancel individual orders of the pair, leaving the remainingorder in the market. The user can cancel both orders in the pairsimultaneously. The user can change the price for an individual order ofthe pair. The user can create a profit/loss bracket order pair. AProfit/Loss bracket is a specific case of an OCO order pair. This orderpair consists of a limit order to establish a profit and a stop lossorder to limit loss. The stop loss portion of the bracket should be ableto be a “trailing stop.” The use is able to create a profit/loss bracketaround an existing position. The user is able to create a profit/lossbracket around a fill. The use can create a profit/loss bracket aroundan order in the filled state.

The user can create trailing stop orders. A trailing stop is an orderthat tracks a price of the instrument and adjusts the stop trigger pricein accordance with a predefined rule (i.e., stop trigger is changed whenthe market changes a certain number of ticks).

Trailing stop orders can be either of type stop or stop limit. For stoplimit orders, the limit price will be changed such that it keeps thesame differential from the stop trigger price. In order to set up thetrailing stop rule, the user must enter: the number of ticks that themarket must change before the stop trigger price should be adjusted. Thenumber of ticks that the stop trigger price should be adjusted when anadjustment is warranted. A trailing stop order is purely synthetic.

The stop order should only be known to the client until it is actuallytriggered. At that time either a market order (in the case of an ordertype of stop) or a limit order (in the case of a stop limit order) willbe entered into the market. A trailing stop only adjusts the stoptrigger price in the profitable direction of the trade. A trailing stoporder to sell does not adjust the stop trigger price to a value lessthan the initial trigger value. A trailing stop order to sell onlyincreases the stop trigger price. A trailing stop order to sell onlyadjusts the stop trigger price when new high prices are traded in theinstrument. This will prevent adjusting the stop trigger price if theinstrument price retraces a profitable move but does not trigger thestop.

A trailing stop order to buy does not adjust the trigger price to avalue greater than the initial trigger value. A trailing stop order tobuy only decreases the stop price. A trailing stop order to buy mustadjusts the trigger price when new low prices are traded in theinstrument. This will prevent adjusting the stop trigger price if theinstrument price retraces a profitable move but does not trigger thestop. Trailing stops are only valid while the user is logged into theapplication 30. Application 30 exit will have the effect of the trailingstop not being in the market. On application exit, if the user hastrailing stops entered, the user will be warned that the stop will notbe worked while the application is closed.

The user is to choose to save trailing stops. On application 30 launch,the user is advised of any saved trailing stops and given theopportunity to reenter them.

The user is able to create parked orders. A parked order is an orderthat is created by the user but not submitted to the market. The user isable to release a parked order. Releasing a parked order submits it tothe market. The user can change a working order to a parked order. Thissends a cancel to the exchange. On receipt of the cancelacknowledgement, the application 30 changes the order state to indicatethat the order is parked. Parked orders are saved on application exit.Parked orders are restored on application 30 launch.

If-Then Strategies

The user can create an “If-Then Strategy.” With an If Then Strategy, anorder is entered into the market. Upon receipt of a fill acknowledgementfor the order, one or more other orders are automatically entered by theapplication 30 based on the If-Then strategy. Typically, the orders thatare entered with If-Then Strategy will be orders to manage profit andloss expectations for the fill that was received on the original order.The user can create an If-Then strategy where on the receipt of theacknowledgement of an order fill, a profit/loss bracket is enteredaround the fill price for the filled quantity. The user can create anIf-Then strategy where on the receipt of the acknowledgement of an orderfill, a stop or stop limit order is entered at an offset from the fillprice for the quantity of the fill. The user can create an If-Thenstrategy where on the receipt of the acknowledgement of an order fill, atrailing stop order is entered at an offset from the fill price for thequantity of the fill. The user can create an If-Then strategy where onthe receipt of the acknowledgement of an order fill, a limit order isentered at an offset from the fill price for the quantity of the fill.The user can create an If-Then strategy where on the receipt of theacknowledgement of an order fill, an OCO order pair is entered.

Black-Box Trading Entities

FIG. 15 is a flow diagram illustrating a Method 88 for automaticallyexecuting a black box trading entity. At Step 90, a black box tradingentity is created for two or more real or synthetic trading entities. AtStep 92, two or more sets of electronic trading information are receivedfrom one or more electronic trading exchanges including tradinginformation for the two or more real or synthetic trading entities forthe created black box trading entity. At Step 94, two or more electronictrades for the black box trading entity are automatically electronicallyexecuted on the appropriate one or more electronic trading exchanges toexecute the black-box trading entity.

Method 88 is illustrated with an exemplary embodiment. However, theinvention is not limited to this embodiment and other embodiments canalso be used to practice the invention.

In such an exemplary embodiment at Step 90, a black box trading entityis created from two or more real or synthetic trading entities.

A black box trading entity includes, but is not limited to, tradingstrategies developed by one or more traders for futures contracts,options contracts, or other instruments for differed shipment ordelivery or otherwise, or other contracts or financial or otherinstruments traded electronically. The black box trading entity may becreated only for sell-side trades, only for buy-sides trades, both buyand sell trades, spreads, and other types of real or synthetic tradesthat can be executed electronically.

A synthetic trading entity is a virtual trading entity equivalent toreal trading entity and is created with two or more real tradingentities. For example, the synthetic trading entity may be a syntheticten year bond contract created from two more existing ten year bondcontracts or two or more non-ten year bond contracts. As anotherexample, the synthetic trading entity may simulate a synthetic ten yearbond contract created from a difference between a cash and futures pricefor a selected financial instrument or financial contract.

In one embodiment, the black box trading entity is created by selectingtwo or more real or synthetic trading entities from the GUI 32 via theABV window 66 or Order Ticket window 84. In another embodiment, theblack box trading entity is created by other than the ABV window 66 orOrder Ticket window 84.

At Step 92, one or more sets of electronic trading information arereceived from one or more electronic trading exchanges on an application30 on a target device 12, 14, 16 including trading information for thetwo or more real or synthetic trading entities for the created black boxtrading entity. For example, the application 30 on the target device 12,14, 16 may receive two or more sets of bond trading information for theexemplary synthetic ten year bond contract used to create the black boxtrading entity.

At Step 94, two or more electronic trades for the black box tradingentity are automatically electronically executed from via theapplication 30 on the target device 12, 14, 16 on the appropriate one ormore electronic trading exchanges 20, 22 to execute the black boxtrading entity.

For example, the black box trading entity may include a synthetic tenyear bond contract. In this example, the application 30 on the targetdevice 12, 14, 16 may automatically execute a sell for a call for afirst real bond contract and automatically execute a buy for a put for asecond real bond contract, on one or more electronic trading exchanges,thereby automatically executing the synthetic ten year bond contract aspart of black box trading entity.

In one embodiment, the application 30 allows a trader to create a blackbox trading entity to setup a strategy to trade two or more distinctmarkets (e.g., cash and futures) which have a pre-determinedrelationship (e.g., one-to-one, two-to-one, multi-to-one, etc.) andautomatically execute one or more electronic trading marketssimultaneously.

In one embodiment, the black box trading entity includes a real orsynthetic spread. As is known in the art, a spread includes a purchaseof one futures delivery month against the sale of another futuresdelivery month of the same commodity; the purchase of one delivery monthof one commodity against the sale of that same delivery month of adifferent commodity; or the purchase of one commodity in one marketagainst the sale of the commodity in another market, to take advantageof a profit from a change in price relationships. The term spread isalso used to refer to the difference between the price of a futuresmonth and the price of another month of the same commodity. A spreadalso applies to options and financial instruments. Synthetic spreads torefer to a difference between two or more different or similar realentities of virtually any kind or real instrument or contract.

In one embodiment, the application 30 includes a black box tradingentity with a configurable slippage factor portion that ispre-determined and configurable trader via the graphical user interface.The configurable slippage factor portion allows the trader to safelyexecute an alternative 2^(nd) leg, 3^(rd) leg, etc. of a trade if aninitial primary trade for a futures contract or cash instrument ismissed.

In another embodiment, the black box trading entity includes aone-to-one or multi-to-one trade from either the cash side or thefutures side first. In another embodiment, the black box trading entityincludes a best cash market to trade from.

In another embodiment, the black box trading entity includes aconfigurable duration portion that allows traders to enter synthetic“one-to-one strategies” which are may or may not be in pre-determinedcash-to-futures ratio, or visa-versa. For example, the configurationduration portion allows a one-to-one real or synthetic trading strategyfor one real cash entity to ten futures real entity ratio, orvisa-versa, one real cash entity and eleven real futures entities, orvisa-versa, etc. depending on the trader's preferences.

In another embodiment, the application 30 also includes a graphicalProfit and Loss (P&L) blotter provides risk monitoring at a firm, group,or trader level. The Multi-Execution Trading System calculates P&L on areal-time basis with Mark to Market functionality. The application 30includes firm wide status messages that can be broadcast to all traderswho are viewing a graphical blotter and it will illustrate actual P&Land not just intraday by including previous days total equity position.

The application 30 also allows traders to receive futures and cashmarket data real-time into a spreadsheet (e.g., Excel, etc.) or from aspreadsheet and allows traders to receive both cash and futures tradesreal-time into and from a spreadsheet.

FIG. 16 is a flow diagram illustrating a Method 96 for automaticallycreating a black box trading entity. At Step 98, a first real orsynthetic trading entity is selected from plural real or synthetictrading entities displayed on a graphical user interface for a creatingblack box trading entity. At Step 100, one or more other real orsynthetic trading entities are selected from plural other real orsynthetic trading entities displayed on the graphical user interface forcreating the black box trading entity. At Step 102, a black box tradingentity is created from the selected first real or synthetic tradingentity and the selected one or more other real or synthetic tradingentities. At Step 104, automatic electronic trading of the black boxtrading entity is provided via the graphical user interface.

Method 96 is illustrated with an exemplary embodiment. However, theinvention is not limited to this embodiment and other embodiments canalso be used to practice the invention.

In such an exemplary embodiment at Step 98, a first real or synthetictrading entity is selected from plural real or synthetic tradingentities displayed on a graphical user interface 32 displayed by anapplication 30 on a target device 12, 14, 16 for a black box tradingentity.

At Step 100, one or more other real or synthetic trading entities areselected from plural other real or synthetic trading entities displayedon the GUI 32 for the black box trading entity.

At Step 102, a black box trading entity is created from the selectedfirst real or synthetic trading entity and the selected one or moreother real or synthetic trading entities

At Step 104, automatic electronic trading of the black box tradingentity is provided via the GUI 32. For example, two or more electronictrades for real or synthetic trading entities comprising the black boxtrading entity are automatically electronically executed on appropriateone or more electronic trading exchanges 20, 22 to execute the black boxtrading entity.

In one embodiment, Step 102 allows a trader to enter one or more desiredtrading formulas directly into the application 30, or extract or usedirectly, one or more trading formulas from a spreadsheet (e.g.,Microsoft Excel, etc.) thereby allowing the application 30 toautomatically execute the black box entity via one or more electronictrading exchanges. The black box entity allows automatic tracking andexecution of both real and synthetic trading entities.

FIG. 17 is a block diagram 106 illustrating creation of a black boxtrading entity. This exemplary block diagram illustrates creation of ablack box trading entity called “MY S&P” 108 created with two OrderTicket windows 84, 84′. Order Ticket window 84 includes a selection of areal trading entity and Order Ticket window 84′ includes a selection ofsynthetic trading entity. In one embodiment synthetic trading entitiesare displayed with a different color 110 that real trading entity todistinguish them for a trader when then are displayed on a Quotes window50.

FIG. 17 illustrates creating an exemplary black box trading entity MYS&P using two or more Order Ticket windows 84, 84′. However, the presentinvention is not limited to such an embodiment and other a synthetictrading entity can be created using the ABV window 66 or otherspecialized windows displayed by the GUI 32.

It should be understood that the architecture, programs, processes,methods and It should be understood that the architecture, programs,processes, methods and systems described herein are not related orlimited to any particular type of computer or network system (hardwareor software), unless indicated otherwise. Various types of generalpurpose or specialized computer systems may be used with or performoperations in accordance with the teachings described herein.

In view of the wide variety of embodiments to which the principles ofthe present invention can be applied, it should be understood that theillustrated embodiments are exemplary only, and should not be taken aslimiting the scope of the present invention. For example, the steps ofthe flow diagrams may be taken in sequences other than those described,and more or fewer elements may be used in the block diagrams.

While various elements of the preferred embodiments have been describedas being implemented in software, in other embodiments hardware orfirmware implementations may alternatively be used, and vice-versa.

The claims should not be read as limited to the described order orelements unless stated to that effect. In addition, use of the term“means” in any claim is intended to invoke 35 U.S.C. §112, paragraph 6,and any claim without the word “means” is not so intended.

Therefore, all embodiments that come within the scope and spirit of thefollowing claims and equivalents thereto are claimed as the invention.

1. A method for automatically executing a black box trading entity,comprising: creating a black box trading entity from two or more real orsynthetic trading entities; receiving two or more sets of electronictrading information from one or more electronic trading exchangesincluding trading information for the two or more real or synthetictrading entities for the created black box trading entity; andautomatically executing two or more electronic trades electronically forthe black box trading entity on the appropriate one or more electronictrading exchanges to execute the black box trading entity.
 2. The methodof claim 1 further comprising a computer readable medium having storedtherein a plurality of instructions for causing one or more processorsto execute the steps of the method.
 3. The method of claim 1 wherein theblack box trading entity includes a real or synthetic trading entitycreated from two or more selected real or synthetic financialinstruments.
 4. The method of claim 1 wherein the black box tradingentity includes a black box trading entity created from two or moreselected real or synthetic financial contracts.
 5. The method of claim 1wherein the black box trading entity includes a black box trading entitycreated from a difference between a cash and futures price for aselected financial instrument or financial contract.
 6. The method ofclaim 1 wherein the black box trading entity includes a black boxtrading entity created from two or more distinct markets including acash market and a futures market.
 7. The method of claim 1 wherein theblack box trading entity includes a black box trading entity createdwith a pre-determined relationship between the two or more real orsynthetic trading entities.
 8. The method of claim 7 wherein thepre-determined relationship includes a one-to-one relationship ormulti-to-one relationship.
 9. The method of claim 1 wherein the blackbox trading entity is created via a graphical user interface byselecting two or more real trading entities from a list of a pluralityof real trading entities.
 10. The method of claim 1 wherein the blackbox trading entity includes a configurable slippage factor portion toexecute an alternative real futures entity trade if a primary realfutures entity trade is missed.
 11. The method of claim 10 whereinconfigurable slippage factor potion is configured from a graphical userinterface.
 12. The method of claim 1 wherein the black box tradingentity includes a configurable duration portion to create one-to-onesynthetic trading durations including multi-to-one real trading entitydurations.
 13. The method of claim 1 wherein the configuration durationportion is configured from a graphical user interface.
 14. The method ofclaim 1 wherein the black box trading entity includes a real orsynthetic spread between two or more real or synthetic trading entities.15. The method of claim 1 wherein the creating step includes creatingthe black box trading entity from an Aggregated Book View or OrderTicket graphical window on a graphical user interface.
 16. A method forautomatically creating a black box trading entity, comprising: selectinga first real or synthetic trading entity from a plurality of real orsynthetic trading entities displayed on a graphical user interface;selecting one or more other real or synthetic trading entities from aplurality of real trading entities displayed on the graphical userinterface; creating a black box trading entity from the selected firstreal or synthetic trading entity and the selected one or more other realor synthetic trading entities; and providing automatic electronictrading of the black box trading entity via the graphical userinterface.
 17. The method of claim 16 further comprising a computerreadable medium having stored therein a plurality of instructions forcausing one or more processors to execute the steps of the method. 18.The method of claim 16 wherein the black box trading entity includes oneor more real or synthetic spreads between one or more real or syntheticentities, one or more real or synthetic one-to-one or multi-to-onetrading durations, or one or more real or synthetic slippage factors toautomatically execute a secondary trade if a primary trade is missed.19. The method of claim 16 wherein the graphical user interface includesan Aggregated Book View or Order Ticket graphical window on thegraphical user interface.
 20. The method of claim 16 wherein thecreating step includes entering a mathematical formula representing areal or synthetic trading entity thereby allowing automatic tracking andexecution of both real and synthetic trading entities.
 21. A black boxtrading entity system, comprising in combination: means for selecting afirst real or synthetic trading entity from a plurality of real orsynthetic trading entities, for selecting one or more other real orsynthetic trading entities from a plurality of real or synthetic tradingentities; means for creating a black box trading entity from theselected first real or synthetic trading entity and the selected one ormore other real or synthetic trading entities; and means for providingautomatic electronic trading of the black box trading entity via one ormore electronic trading exchanges.
 22. The black box trading system ofclaim 21 wherein the black box trading entity includes one or more realor synthetic spreads between one or more real or synthetic entities, oneor more real or synthetic one-to-one or multi-to-one trading durations,or one or more real or synthetic slippage factors to automaticallyexecute a secondary trade if a primary trade is missed.
 23. A black boxtrading entity system, comprising in combination: a graphical userinterface with a plurality of windows for creating and displaying astatus electronic trades for a black box trading entity; an applicationfor displaying the graphical user interface, for receiving two or moresets of electronic trading information from one or more electronictrading exchanges including trading information for the black boxtrading entity, for automatically executing two or more electronictrades electronically for the black box trading entity on theappropriate one or more electronic trading exchanges and for displayingresults on the graphical user interface.